feat(analytics): report to collect.mindshub.ai and send an identifying agent (ENG-1355) - #611

User story

As a whoever is asked how many people finish the installer, accept terms, or pick BYOK
I want the desktop app's four install events to actually arrive in PostHog
So that the onboarding funnel can be answered from data rather than guessed at

Why this matters

None of the four ANTONAPP_* events has ever reached PostHog. The collector they were pointed at relayed an event only when its action name started with a lowercase anton_ or ds_connect_, and that match is case sensitive. These names are uppercase, so every one of them was discarded. The endpoint answered HTTP 200 while doing it, and sendEvent reads no response, so nothing anywhere reported it.

This was found while fixing the same defect for anton's per-turn cost event, which is the ticket's original subject. The blast radius turned out to include the install funnel.

What happens today

flowchart LR
  I["installer.ts:563<br/>ANTONAPP_INSTALLATION_SUCCESS"] --> S["sendEvent"]
  X["index.ts:1146-1151<br/>TERMS_ACCEPTED, MINDSLLM, BYOK"] --> S
  S --> L{"zoomInfoCollector"}
  L -->|"action starts with lowercase<br/>anton_ or ds_connect_"| P["PostHog 355390"]
  L -->|"ANTONAPP_* is uppercase,<br/>so it never matches"| D["discarded"]
  D --> R["HTTP 200"]
  R --> Q["sendEvent discards the response.<br/>Four events, zero rows, no signal."]

What should happen

flowchart LR
  I["installer.ts:563<br/>ANTONAPP_INSTALLATION_SUCCESS"] --> S["sendEvent, User-Agent set"]
  X["index.ts:1146-1151<br/>TERMS_ACCEPTED, MINDSLLM, BYOK"] --> S
  S --> L{"collect.mindshub.ai"}
  L -->|"no action filter,<br/>properties minus a denylist"| P["PostHog 355390"]
  L --> M["EventsRelayed counter<br/>plus a Slack alarm"]

What changed

The README section exists because these two paths get conflated. The renderer has posthog-js keyed on the signed-in Keycloak user and configured by VITE_POSTHOG_MINDSHUB_MAIN_PROJECT_TOKEN. The main process has this beacon, which identifies nothing and is configured by a constant. Anyone debugging "why is this event missing" needs to know which one they are looking at.

One gap recorded, not fixed here. sendEvent sends no installation fingerprint, unlike anton's send_event, which sends aid. So these four events cannot be attributed to a machine. The collector groups them under one synthetic id and stamps aid_missing on them so the gap is queryable rather than invisible. Sending an install id is a small follow-up and is deliberately outside this change.

Rollout, which is different here

src/main/** has no OTA path, so this constant reaches users only when they download a new installer. That is worth saying out loud because it means the fix lands slowly. It costs nothing, though: these events are already dark for every existing install, so nothing regresses while the change propagates, and every new installer from here reports correctly.

Acceptance criteria

• A fresh install driven to completion produces one ANTONAPP_INSTALLATION_SUCCESS row in project 355390 within 60 seconds.
• Accepting terms produces ANTONAPP_TERMS_ACCEPTED; each provider choice produces ANTONAPP_MINDSLLM or ANTONAPP_BYOK.
• Those rows carry aid_missing set, and a distinct_id that is the collector's synthetic id rather than a real fingerprint.
• Still true afterwards: sendEvent throws nothing when the endpoint is unreachable or refuses the request.
• Still true afterwards: no event carries conversation content, a file path, or an email address.

How to test

1. Merge order matters. mindsdb/mindshub_services#186 and mindsdb/terraform#162 must be deployed first. Confirm with curl -s "https://collect.mindshub.ai/collect?action=ANTONAPP_TERMS_ACCEPTED&aid=qaprobe1355" returning relayed: true. That call alone proves the case-sensitivity fix, since the same request against the old endpoint returns posthogResult: false.
2. npm run pack, clear install state per the README's fresh-install reset (anton-reset --deep), and run the app through first-run.
3. Accept terms, then pick MindsLLM or BYOK.
4. Wait 60 seconds, then in project 355390: select event, properties.aid_missing from events where event like 'ANTONAPP%' order by timestamp desc limit 10. Expect one row per step above.
5. Confirm the failure path: point ANALYTICS_URL at an unroutable host in a local build and confirm first-run completes with no error surfaced.

Verified locally

Both re-run after rebasing onto current staging, which needed an npm install for a dependency added in the meantime.

Ships with

• mindsdb/mindshub_services#186, the collector.
• mindsdb/terraform#162, the host and the alarms.
• feat(analytics): report to collect.mindshub.ai and send an identifying agent (ENG-1355) anton#333, the same repoint for the per-turn cost event.

Refs ENG-1355